Add prompt format strings for socket connections#1563
Conversation
scottnemes
left a comment
There was a problem hiding this comment.
Verified new socket related prompt options display as expected.
ce909d9 to
ee63819
Compare
|
Findings
Missing tests / edge cases
Security
Notes
If you want, I can propose the exact test cases or a minimal patch to make basename extraction portable. |
ee63819 to
ca84bf7
Compare
* \j - connection socket basename * \J - full connection socket path * \k - connection socket basename OR the port * \K - full connection socket path OR the port the most handy of which is probably \k, which will show the socket basename if it exists, and if not, the port. Incidentally, further fix up the prompt commentary in myclirc files.
|
Findings (ordered by severity)
Missing tests / edge cases
Notes
|
ca84bf7 to
f16cd59
Compare
|
Findings (ordered by severity)
No security issues spotted. If you want, I can add the missing tests. |
Description
\j- connection socket basename\J- full connection socket path\k- connection socket basename OR the port\K- full connection socket path OR the portthe most handy of which is probably
\k, which will show the socket basename if it exists, and if not, the port.Incidentally, further fix up the prompt commentary in myclirc files.
Checklist
changelog.mdfile.AUTHORSfile (or it's already there).